home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / p_man / cat3n / t_rcvdis.z / t_rcvdis
Encoding:
Text File  |  2002-10-03  |  9.1 KB  |  199 lines
  1.  
  2.  
  3.  
  4. tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))                                                      tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss - retrieve information from disconnect
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_ffff_dddd_eeee_ffff ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_xxxx_tttt_iiii_...._hhhh_>>>>
  14.      _####_eeee_llll_ssss_eeee
  15.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_tttt_iiii_uuuu_ssss_eeee_rrrr_...._hhhh_>>>>
  16.      _####_eeee_nnnn_dddd_iiii_ffff
  17.  
  18.      _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss _((((_iiii_nnnn_tttt _ffff_dddd_,,,, _ssss_tttt_rrrr_uuuu_cccc_tttt _tttt______dddd_iiii_ssss_cccc_oooo_nnnn _****_dddd_iiii_ssss_cccc_oooo_nnnn_))))_;;;;
  19.  
  20. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.      This function is used to identify the cause of a disconnect, and to
  22.      retrieve any user data sent with the disconnect.  _ffff_dddd identifies the local
  23.      transport endpoint where the connection existed, and _dddd_iiii_ssss_cccc_oooo_nnnn points to a
  24.      _tttt______dddd_iiii_ssss_cccc_oooo_nnnn structure containing the following members:
  25.  
  26.           _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_bbbb_uuuu_ffff _uuuu_dddd_aaaa_tttt_aaaa_;;;;
  27.           _iiii_nnnn_tttt _rrrr_eeee_aaaa_ssss_oooo_nnnn_;;;;
  28.           _iiii_nnnn_tttt _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee_;;;;
  29.  
  30.      _nnnn_eeee_tttt_bbbb_uuuu_ffff is described in _iiii_nnnn_tttt_rrrr_oooo(3N).  _rrrr_eeee_aaaa_ssss_oooo_nnnn specifies the reason for the
  31.      disconnect through a protocol-dependent reason code, _uuuu_dddd_aaaa_tttt_aaaa identifies any
  32.      user data that was sent with the disconnect, and _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee may identify an
  33.      outstanding connect indication with which the disconnect is associated.
  34.      _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee is only meaningful when _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss is issued by a passive
  35.      transport user who has executed one or more _tttt______llll_iiii_ssss_tttt_eeee_nnnn functions and is
  36.      processing the resulting connect indications.  If a disconnect indication
  37.      occurs, _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee can be used to identify which of the outstanding connect
  38.      indications is associated with the disconnect.
  39.  
  40.      If a user does not care if there is incoming data and does not need to
  41.      know the value of _rrrr_eeee_aaaa_ssss_oooo_nnnn or _ssss_eeee_qqqq_uuuu_eeee_nnnn_cccc_eeee, _dddd_iiii_ssss_cccc_oooo_nnnn may be _NNNN_UUUU_LLLL_LLLL and any user
  42.      data associated with the disconnect will be discarded.  However, if a
  43.      user has retrieved more than one outstanding connect indication (via
  44.      _tttt______llll_iiii_ssss_tttt_eeee_nnnn) and _dddd_iiii_ssss_cccc_oooo_nnnn is _NNNN_UUUU_LLLL_LLLL, the user will be unable to identify which
  45.      connect indication the disconnect is associated with.
  46.  
  47.      This function resides within both the X/Open compliant _llll_iiii_bbbb_xxxx_nnnn_eeee_tttt and the
  48.      SVR4 compliant _llll_iiii_bbbb_nnnn_ssss_llll Network Services libraries.  Network Services
  49.      applications which require X/Open compliance must link-load with _----_llll_xxxx_nnnn_eeee_tttt.
  50.      Network Services applications which require SVR4 compliance must link-
  51.      load with _----_llll_nnnn_ssss_llll.
  52.  
  53.      On failure, _tttt______eeee_rrrr_rrrr_nnnn_oooo may be set to one of the following:
  54.  
  55.      _TTTT_BBBB_AAAA_DDDD_FFFF               The specified file descriptor does not refer to a
  56.                          transport endpoint.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))                                                      tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      _TTTT_NNNN_OOOO_DDDD_IIII_SSSS              No disconnect indication currently exists on the
  75.                          specified transport endpoint.
  76.  
  77.      _TTTT_BBBB_UUUU_FFFF_OOOO_VVVV_FFFF_LLLL_WWWW           There are two different conditions in which _TTTT_BBBB_UUUU_FFFF_OOOO_VVVV_FFFF_LLLL_WWWW
  78.                          will be returned.  If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined _aaaa_nnnn_dddd
  79.                          the number of bytes allocated for incoming data is
  80.                          _gggg_rrrr_eeee_aaaa_tttt_eeee_rrrr _tttt_hhhh_aaaa_nnnn _zzzz_eeee_rrrr_oooo _aaaa_nnnn_dddd is not sufficient to store the
  81.                          data.  If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is _nnnn_oooo_tttt defined and the number
  82.                          of bytes allocated for incoming data is not
  83.                          sufficient to store the data.  The provider's state,
  84.                          as seen by the user, will change to _TTTT______IIII_DDDD_LLLL_EEEE, and the
  85.                          disconnect indication information to be returned in
  86.                          _dddd_iiii_ssss_cccc_oooo_nnnn will be discarded.
  87.  
  88.      _TTTT_NNNN_OOOO_TTTT_SSSS_UUUU_PPPP_PPPP_OOOO_RRRR_TTTT         This function is not supported by the underlying
  89.                          transport provider.
  90.  
  91.      _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE           If ______XXXX_OOOO_PPPP_EEEE_NNNN______SSSS_OOOO_UUUU_RRRR_CCCC_EEEE is defined and _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss() is issued
  92.                          in the wrong sequence on the transport endpoint
  93.                          referenced by _ffff_dddd, the _TTTT_OOOO_UUUU_TTTT_SSSS_TTTT_AAAA_TTTT_EEEE error value is
  94.                          returned within the variable _tttt______eeee_rrrr_rrrr_nnnn_oooo.
  95.  
  96.      _TTTT_SSSS_YYYY_SSSS_EEEE_RRRR_RRRR             A system error has occurred during execution of this
  97.                          function.
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.  
  134.  
  135.  
  136. tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))                                                      tttt____rrrrccccvvvvddddiiiissss((((3333NNNN))))
  137.  
  138.  
  139.  
  140. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  141.      _iiii_nnnn_tttt_rrrr_oooo(3N), _tttt______aaaa_llll_llll_oooo_cccc(3N), _tttt______cccc_oooo_nnnn_nnnn_eeee_cccc_tttt(3N), _tttt______llll_iiii_ssss_tttt_eeee_nnnn(3N), _tttt______oooo_pppp_eeee_nnnn(3N),
  142.      _tttt______ssss_nnnn_dddd_dddd_iiii_ssss(3N)
  143.  
  144. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  145.      _tttt______rrrr_cccc_vvvv_dddd_iiii_ssss returns 0 on success and -1 on failure and _tttt______eeee_rrrr_rrrr_nnnn_oooo is set to
  146.      indicate the error.
  147.  
  148.  
  149.  
  150.  
  151.  
  152.  
  153.  
  154.  
  155.  
  156.  
  157.  
  158.  
  159.  
  160.  
  161.  
  162.  
  163.  
  164.  
  165.  
  166.  
  167.  
  168.  
  169.  
  170.  
  171.  
  172.  
  173.  
  174.  
  175.  
  176.  
  177.  
  178.  
  179.  
  180.  
  181.  
  182.  
  183.  
  184.  
  185.  
  186.  
  187.  
  188.  
  189.  
  190.  
  191.  
  192.  
  193.  
  194.  
  195.                                                                         PPPPaaaaggggeeee 3333
  196.  
  197.  
  198.  
  199.